@sankho thanks for this! I was able to take what you did here and combine it with a rewrite of the examples in #2 so that I can demonstrate parity with the examples at https://datamaps.github.io. Can you check out the src/datamaps.jsx changes in #2 and let me know what you think?

I didn't include the resetOnUpdateChoropleth option in #2 yet. What does the reset option do there?

@btmills the update branch looks great, like the transition to using the ES6 class approach as opposed to the old ES5 approach.

resetOnUpdateChoropleth, or as you say the reset option on the datamaps' updateChoropleth method - resets the map of all data when you call updateChoropleth. So if it's set to true, the updating data will overwrite the previous dataset, where if it's set to false, it will be additive / merged in w/ the old dataset.

Would love to build on top ofyour changes - I pushed a few more changes to my branch to deal with a few bugs I caused but it's all in the old React component form, would like to move on to the latest. LMK if you merge it in and I can make another PR!

@sankho thanks for the explanation! I added an updateChoroplethOptions prop in 4b6acf3. The datamaps v0.4.4 release notes said reset is the only key it cares about now, but having users pass in updateChoroplethOptions={{ reset: true }} makes it forward-compatible without any updates here if there are other options added later.

I just merged #2, so you should be good to start building on top of it (and sorry about the merge conflicts 😳 ).

@btmills actually the changes you made in #2 satisfy my needs. Gonna move onto solving issue #3 next.

Examples page looks great btw!